Method and system to process navigation information

ABSTRACT

A system to process navigation information includes a receiving module to receive a data request from a network entity. The data request includes a network entity identifier that uniquely identifies the network entity. The system further includes an application to generate a network event based on the data request, the network event including the navigation information. Finally, the system includes a publisher module to communicate the network event to a first server that is distinguished from a first plurality of servers based on the network entity identifier.

RELATED APPLICATIONS

This application is a continuation of and claims the benefit of priority to U.S. patent application Ser. No. 15/066,695, filed Mar. 10, 2016, which is a continuation of and claims the benefit of priority to U.S. patent application Ser. No. 11/322,572, filed Dec. 30, 2005, which claims the benefit of priority to U.S. Provisional Patent Application Ser. No. 60/736,906, filed Nov. 15, 2005, the benefit of priority of each of which is claimed hereby, and each of which are incorporated by reference herein in its entirety.

TECHNICAL FIELD

An embodiment relates generally to the technical field of network processing and, in one example embodiment, to a method and system to process navigation information.

BACKGROUND

Most websites with sizeable traffic require thousands of application servers to respond to data requests from users. Such a website may include application servers that may be organized according to server-farms or pools that may be respectively located at different physical locations and respond to data requests for different types of user interfaces. For example, one pool of application servers may responds to data requests for user interfaces that contain search results and another pool of application servers may respond to data requests for user interfaces that contain user profile information.

Websites that desire to track information (e.g., navigation information) associated with a user that is navigating the website may maintain a log-file at each application server. Unfortunately, tracking all the navigation information of a specific user requires accessing the log-files residing on the thousands of machines in different physical locations and merging the information according to Internet protocol address to maintain the identify of the user and according to time to maintain the chronology of the user activity. This operation is expensive and typically performed off-line thereby introducing a lag between the time the data is recorded in the log-file and the time the data may be available for analysis.

SUMMARY

According to a first aspect of the disclosure there is described a method to process navigation information. The method includes receiving a data request from a network entity, the data request including a network entity identifier that uniquely identifies the network entity; generating a network event based on the data request, the network event including the navigation information; communicating the network event to a first server that is distinguished from a first plurality of servers based on the network entity identifier.

According to a second aspect of the disclosure there is described a method to process navigation information. The method includes receiving a data request from a network entity, the data request including a network entity identifier that uniquely identifies the network entity; generating a network event based on the data request, the network event including the navigation information; and analyzing the network event in real time.

BRIEF DESCRIPTION OF THE DRAWINGS

An embodiment of the present disclosure is illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which:

FIG. 1 is a network diagram depicting a system, according to one example embodiment of the present disclosure;

FIG. 2 is a block diagram illustrating a system, according to an example embodiment of the present disclosure;

FIG. 3 is a block diagram illustrating database tables, according to one embodiment;

FIG. 4 is a representation of a data request, according to one embodiment;

FIG. 5 is a representation of a network event, according to one embodiment;

FIG. 6 is a representation of data response, according to one embodiment;

FIG. 7A is a block diagram illustrating a robot table, according to one embodiment;

FIG. 7B is a block diagram illustrating a robot work area, according to one embodiment;

FIG. 8 is a block diagram illustrating a publisher table, according to one embodiment;

FIG. 9 is a block diagram illustrating a buffer, according to one embodiment;

FIG. 10 is a block diagram illustrating a navigation data table, according to one embodiment;

FIG. 11 is a flowchart illustrating a method, according to one embodiment, to process navigation information;

FIG. 12 is a flowchart illustrating a method, according to one embodiment, to generate a network event;

FIG. 13 is a flowchart illustrating a method, according to one embodiment, to flush a buffer to a database;

FIG. 14 is a flowchart illustrating a method, according to one embodiment, to generate cookies;

FIG. 15 is a flowchart illustrating a method, according to one embodiment, to save data requests;

FIG. 16 is a flowchart illustrating a method, according to one embodiment, to identify a robot;

FIG. 17 is a block diagram of a machine, according to one embodiment.

DETAILED DESCRIPTION

A method and system to process navigation information are described. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. It will be evident, however, to one skilled in the art that the present disclosure may be practiced without these specific details.

FIG. 1 is a network diagram depicting a system 10, according to one example embodiment of the present disclosure, having a client-server architecture. A platform, in the example form of an information storage and retrieval platform 12, provides server-side functionality, via a network 14 (e.g., the Internet) to one or more clients 20, 22 (e.g., network entities). FIG. 1 illustrates, for example, a web client 16 (e.g., a browser, such as the INTERNET EXPLORER browser developed by Microsoft Corporation of Redmond, Wash. State) executing on the client machine 20 and a programmatic client 18 or software agent (e.g., a robot such as the PIXIEROBOT, an automated Web Scraping Tool, made by PixiEware™ Software of Ontario, Canada or WEB SCRAPER PLUS made by velocityscape of Scottsdale, Ariz.) executing on client server machine 22. Further, the client machines 20, 22 are shown to store cookies including a network entity identifier 23, a time 25, and a clock count 27.

Turning specifically to the information storage and retrieval platform 12, an application program interface (API) server 24 and a web server 26 are coupled to, and provide programmatic and web interfaces respectively to, one or more application servers 28. The application servers 28 may be aggregated into pools and include applications 30 that may be dedicated to respond to specific types of data requests from the client machines 20, 22. For example, one pool of applications 30 may be dedicated to processing queries from the client machines 20, 22 and returning a user interface (e.g., data response) that includes search results. Another pool of applications 30 may be dedicated to processing requests from the client machines 20, 22 to return a user interface that displays a user profile. In addition, the applications 30 may generate a network event that includes navigation information for each data request/data response processed. Thus, user activity may be tracked for all users of the information storage and retrieval platform 12. The application servers 28 are, in turn, shown to be coupled to a processing server 38 that hosts a publisher module 40 and database servers 34. The publisher module 40 receives network events from the application servers 28 and communicates the network events over a bus 41 to multiple processing servers 38 that host respective listener modules 42. The host listener modules 42, in turn, are shown to communicate with database servers 34 that may be utilized to store and retrieve information to and from the databases 36. The components utilizing the bus 41 (e.g., publisher module 40, listener modules 42, etc.) may be publish/subscribe middleware software that may be embodied as TIBCO RENDEZVOUS™, a middleware or Enterprise Application Integration (EAI) product developed by Tibco Software, Inc. of Palo Alto, Calif.

While the system 10 shown in FIG. 1 employs a client-server architecture, the present disclosure is of course not limited to such an architecture, and could equally well find application in a distributed, or peer-to-peer, architecture system. The receiving module 37, applications 30, publisher module 40, and listener modules 42 may also be implemented as standalone software programs, which do not necessarily have networking capabilities.

The web client 16, it will be appreciated, accesses the various services and functions provided by applications via the web server 26 supported by the web server 26. Similarly, the programmatic client 18 accesses the various services and functions provided by the applications 30 via the programmatic interface provided by the API server 24.

The information storage and retrieval platform 12 may be embodied as the WORLDS ONLINE MAKETPLACE provided by eBay of San Jose, Calif. For example, sellers may post listings or items for goods and services that may be purchased by buyers or won in auctions by bidders.

Processing Navigation Information

FIG. 2 is a block diagram illustrating a search system 46 as embodied in the information storage and retrieval platform 12, according to an example embodiment of the present disclosure. The search system 46 is presented to provide an overview of processing navigation information.

At operation 47, a user at the client machine 20 utilizes the web client 16 (e.g., web browser) to a query for “Dr. Seuss Books.” The web client 16 generates a data request that includes the query and may further include a network entity identifier 23, a time 25, and a click count 27. In one embodiment, the network entity identifier 23 may be a thirty-two character hexadecimal value that may be utilized to uniquely identify the client machine 20 (e.g., network entity). The time 25 chronicles the time the previous data request was received from the client machine 20. The click count 27 is an ascending count (e.g., 1, 2, 3, . . . etc.) that identifies a particular data request within a particular session, as described more fully below.

At operation 48, the receiving module 37 receives a data request from the client machine 20 and determines which application server(s) 28 are appropriate to process the query. For example, application server(s) 28 that process queries and generate user interfaces that include search results may be appropriate. At operation 50, the receiving module 37 routes the data request to the appropriate application server 28. At operation 52, the application 30 generates a data response (e.g., search results) based on the query and communicates the data response back to the receiving module 37 which, in turn, at operation 54, communicates the data response back to the client machine 20. Further, the application 30 may generate a network event that describes the data request/data response (e.g., navigation information) and, at operation 56, communicates the network event to the publisher module 40. The publisher module 40 receives the network event and generates a hash value based on the network entity identifier 23. The hash value may be used to determine an address of a listener module 42. At operation 58, the publisher module 40 uses the address to communicate the network event to the appropriate listener module 42 over the bus 41. At operation 60, the listener module 42 receives the network event and stores the network event in a buffer A or B. Further, at operation 62 the listener module 42 periodically writes the contents of a buffer A or B to the database 36.

The above example overview describes a data request that included a query for a user interface that contains search results; however, it will be appreciated that other embodiments may describe a data requests for other types of user interfaces (e.g., web pages).

Session

In one embodiment a session may be defined as a set of data requests where the time between any two data request is less than or equal to a predetermined time period (e.g., thirty minutes.) Thus, a data request that is received thirty one minutes after receiving the previous data request may be considered the first data request in the next session. Other embodiments may define a session to be longer or shorter in duration.

Successive data requests within a session are chronicled with the click count 27. For example, the click count of the first data request in a session is one and the click count of the second data request in the session is two. The click count 27 may be copied from the data request into the network event data structure 86 to chronicle the click count 27. The click count 27 may be reset to one by the application 30 based on the time 25. For example, the application 30 may reset the click count to one if the difference between the current time and the time 25 in the data request is greater than the predetermined session threshold.

Generating and Maintaining Cookies

Client machines 22, 20 may generate data requests without cookie information (e.g., network entity identifier 23, time 25, click count 27). For example a web client 16 that has never communicated a data request to the information storage and retrieval platform 12 may not include a network entity identifier, time 25, or a click count 27 in the data request. Further, client machines 22 with programmatic clients (e.g., robots) typically do not permit cookies to be stored at the client machine 22 and consequently may generate data requests to the information storage and retrieval platform 12 without cookie information.

The application(s) 30 may respond to a data request without cookie information by generating the cookie information and appending the cookie information to the response (e.g., data response). At the client machines 20, 22 the cookie information may be stored in a local storage device (e.g., cache, disk, etc.) and communicated back to the information storage and retrieval platform 12 the next data request.

Analyzing Network Events

The listener modules 42 may analyze the network events in real-time or offline. The listener modules 42 analyze network events in real-time by reading network events as they are received from the bus 41. The listener modules 42 may analyze network events offline by reading network events from the database 36.

An example of analyzing the network events in real-time may include the listener modules 42 at each processing server 38 collecting a requested webpage identifier (e.g., user interface identifier) from each network event responsive to reception of the network event data structure 86. The listener module 42 may collect the user interface identifier for a period of time to generate a report that maintains a frequency of data requests for a type of webpage (e.g., user interface). Such a report may be used to identify the most frequently requested type of user interface, the median requested type of user interface and the least frequently requested type of interface for the period of time. Further, it will be appreciated that not every network event that may be generated for the period of time requires collection; rather, sampling may be employed. Sampling may be employed by utilizing fewer than all of the listener modules 42. For example, if ten listener modules 42 may be used to process all the network events then five listener modules 42 may be used to process fifty percent of the network events. Note that employing sampling in this manner may maintain the integrity of a session because all network events originating from a particular network entity should be processed by the same listener module 42.

An example of analyzing the network events in an offline mode may include the listener modules 42 at each processing server 38 collecting the network events to identify robots. Programmatic clients 18 (e.g., robots) present a special problem because they sometimes prevent cookies from being stored on the client machine 22 where they execute. For example, before a robot is identified, each network event originating from the robot may be stored with a different network entity identifier 23 but the same client internet protocol address. Analyzing the network events in the offline mode enables the listener module 42 to identify this pattern. In response, the listener module 42 may allocate a network entity identifier 23 that may be stored in the database 36 in association with the client internet protocol address. Accordingly, the application 30 may utilize the database 36 to identify a network event as associated with a robot based on the client internet protocol address and update the network event with the network entity identifier 23 provided in the robot table.

FIG. 3 is a block diagram illustrating database tables 68 according to one embodiment, stored at the information storage and retrieval platform 12. The database tables 68 include a robot table 70, a publisher table 72, and a navigation data table 74. The robot table 70 may be utilized by the application 30 to determine whether the client internet protocol address contained in a data request maps to a network entity identifier 23 associated with a robot. The publisher table 72 may be utilized by the publisher module 40 to route the network event to the appropriate listener module 42. The navigation data table 44 may be used to store network events for subsequent retrieval and analysis.

FIG. 4 is a representation of a data request 76, according to one embodiment. The data request 76 is generated by a web client 16 and is shown to include a network entity identifier 23, a time 25, a click count 27, a user interface identifier 78, a current user interface identifier 80, a referrer user interface identifier 82, a client Internet protocol (IP) address 84, and parameters 85.

The network entity identifier 23 identifies the network entity that communicated the data request 76 to the information storage and retrieval platform 12. The time 25 chronicles the transmission time of the last data request originating from the network entity identified by the network entity identifier 23 in the data request 76. The click count 27 identifies the selection in the current session (e.g., first, second, third, etc.). The user interface identifier 78 identifies the user interface requested with the data request 76. For example, the user interface identifier 78 may identify a user interface that contains search results (e.g., based on a query). Another example of the user interface identifier 78 may include a user interface identifier 78 that identifies a user profile page. The current user interface identifier 80 identifies the user interface currently displayed at the client machine 20. The referrer user interface identifier 82 identifies the user interface previously displayed at the client machine 20. The client Internet protocol (IP) address 84 identifies the Internet protocol (IP) address from which the data request 76 was communicated. Finally, the parameters field 85 may include additional information necessary to process the data request 76 (e.g., query parameters, keywords, user name, etc.).

FIG. 5 is a representation of a network event data structure 86, according to one embodiment. The network event data structure 86 includes navigation information and is generated by the application 30 in response to receiving the data request 76. The network event data structure 86 includes an address 88, the data request 76, a robot flag 90, a hash 92, flag information 94 and tag information 96. The address 88 may be used to route the network event data structure 86 to a particular processing server 38 and listener module 42. The data request 76 has already been described and is included in the network event data structure 86. The robot flag 90 indicates whether or not the client Internet protocol (IP) address 84 in the data request 76 may be associated with a robot. For example, an asserted flag may indicate a robot. The hash 92 may be a value generated by the publisher module 40 based on the network entity identifier 23. The hash 92 may be used to route the network event data structure 86 to one of multiple listener modules 42. The hash algorithm may be selected to generate a hash for any desired number of listener modules 42. For example, the hash 92 algorithm may be selected to generate hash values for ten or twenty listener modules 42 operating on respective processing servers 38. Expansion of the number of hash values may facilitate the addition of processing servers 38 to support additional network traffic due to an increase in the number of network events. The flag information 94 includes bits or flags that may be utilized to register data that is collected from the data request 76 and/or the data response 100. For example, a bit that corresponds to data collected from the data request 76 may be asserted to indicate the user requires a search with exact matching of the words in the query. Another bit may correspond to data that is collected from the data response 100. For example, a bit may be asserted to indicate the search results included a picture. In addition, the tag information 96 may include name/value pairs that may be utilized to register data that is collected from the data request 76 and/or the data response 100. For example, a name/value pair that corresponds to data collected from the data request 76 may indicate whether or not a query may be performed across the category “toys.” Another name/value pair may correspond to data that is collected from the data response 100. For example, a name/value pair may indicate the number of search results to be twenty-three.

FIG. 6 is a representation of a data response 100, according to one embodiment. The data response 100 includes a user interface 102, the network entity identifier 23, the time 25, and the click count 27. The data response 100 may be generated by the application 30 responsive to receiving the data request 76. The user interface 102 may be identified with the user interface identifier 78 in the data request 76. For example, the user interface may include search results that were generated in response to a query from a user operating a web client 16 (e.g., browser). The network entity identifier 23 identifies the network entity that generated the data request 76. The time 25 chronicles the time the data request 76 (e.g., corresponding to the present data response 100) was received from the client machine 20. The click count 27 may be copied from the data request 76 and incremented by one. Subsequent to communication of the data response 100 back to the client machine 20, 22, the network entity identifier 23, time 25, and click count 27 are written to a storage device on the client machine 20, 22 as cookies.

FIG. 7A is a block diagram illustrating a robot table 70, according to one embodiment. Each entry in the robot table 70 may include a client Internet protocol (IP) address 84 and a network-entity identifier 23. An entry in the robot table 70 indicates that a robot operates at the client internet protocol address 84. The robot table 70 may be used by the application 30 to update the robot flag 90 field in the network event data structure 86 and to update the network entity identifier 23 in the network event data structure 86.

FIG. 7B is a block diagram illustrating a robot work area 71, according to one embodiment. Each entry in the robot work area 71 may include a client Internet protocol (IP) address 84 and request information 69 that further includes one or more data requests 76. The robot work area 71 may be used by the listener modules 42 to identify robots and update the robot table accordingly.

FIG. 8 is a block diagram illustrating a publisher table 72, according to one embodiment. Each entry includes a hash 92 and an address 88. The hash 92 may be generated by the publisher module 40 based on the network entity identifier 23. The publisher module 40 may utilize the publisher table 72 to map the hash 92 to an address 88 that may be utilized to identify a particular listener module 42 on the bus 41.

FIG. 9 is a block diagram illustrating a buffer 106, according to one embodiment. The buffer 106 is duplicated on each processing server 38 and may be identified as buffers “A” and “B.” For example one buffer 106 may be used by a listener module 42 to store network events 86 while the other buffer 106 may be used by the listener module 42 to flush or write network events to the database 36. Periodically the listener module 42 may switch the roles of the buffers.

Buffer 106 is shown to include session bins 107. Each session bin 107 may be used to collect network events 86 for a particular session for a particular network entity. To this end, each session bin 107 includes a network entity identifier 23, a time 25, and network event information 110. The network entity identifier 23 identifies the network entity that caused the network event data structure 86 to be generated. The time 25 chronicles the time that the data request was received that was used to generate the network event data structure 86. The network event information 110 includes the network events 86 for the particular session for the particular network entity.

FIG. 10 is a block diagram illustrating an example navigation data table 74. The navigation data table 74 is shown to include network entity profiles 114. The network entity profiles 114 correspond to network entities. Each network entity profile 114 may be associated with multiple sessions 116. Each session 116, in turn, may be associated with multiple network events 86. The navigation data table 74 may be used to facilitate long term storage of network events 86. Further, the listener module 42 may analyze the network information in the navigation data table 74 to generate reports and/or trigger other activity.

FIG. 11 is a flow chart illustrating the method 120, according to one embodiment, to process navigation information. Illustrated on the left are operations performed by the client machine 20, and illustrated on the right are operations performed by the information storage and retrieval platform 12.

The method 120 commences at operation 122 with a user operating the client machine 20. For example the user may enter a search query “Dr. Seuss” to search for Dr. Seuss books that may be listed for sale on the information storage and retrieval platform 12. The information storage and retrieval platform 12 does not require that the user be logged on (e.g., provide a user name and password) to capture navigation information as the user navigates through the user interfaces served by the information storage and retrieval platform 12: rather, the user may navigate anonymously.

At operation 124, the web client 16 at the client machine 20, generates a data request 76. For example, the data request 76 may include a network entity identifier 23, a time 25, and a click count 27 that are copied from cookies at the client machine 20 to the data request 76. Further, the data request 76 may include a user interface identifier 78 that may contain search results, a referrer user interface identifier 82, a client Internet protocol (IP) address 84, and parameters 85 that may include the keywords “Dr. Seuss.” At operation 126, the web client 16 communicates the data request 76 to the information storage and retrieval platform 12.

At operation 128, the receiving module 37 receives the data request 76. The receiving module 37 utilizes the user interface identifier 78 to identify the appropriate application server 28. For example, the present data request 76 may include a user interface identifier 78 that identifies a user interface that contains search results. Accordingly, a processing server 38 that processes queries to generate user interfaces that contain search results may be selected.

At operation 130, the receiving module 37 routes the data request 76 to the appropriate application server 28. At operation 132, an application 30, at the application server 28, generates a data response 100 based on the data request 76. For example, the application 30 may generate a user interface that contains search results; copy the network entity identifier 23 from the data request 76 to the data response 100; stamp the data response 100 with the current time 25; and, update the click count 27. For example, the application 30 may get the click count 27 from the data request, increment the click count 27 by one, and store the incremented click count 27 in the data response 100 or if the different between the current time and the time 25 in the data response 100 is greater than the session time then the application 30 may set the click count 27 in the data response 100 to one.

At operation 134, the application 30 communicates the data response to the client machine 20.

At operation 136, the client machine 20 receives the data response 100 and at operation 138 the client machine 20 stores the network entity identifier 23, the time 25, and the click count 27 as one or more cookies. Finally, the web client 16 displays the user interface 102 to the user operating the client machine 20.

At operation 140, at application server 28, the application 30 generates a network event data structure 86 that includes navigation information that describes the keyword search and the results that are generated, as described on FIG. 12, according to one embodiment.

At operation 142, the application 30 communicates the network event data structure 86 to the publisher module 40.

At operation 144, at the processing server 38, the publisher module 40 receives the network event data structure 86 and generates a hash value. For example, the publisher module 40 may include a hash algorithm to generate a value based on two digits of the 32 digit network entity identifier 23 to generate a value between 0 and 256. Next, the publisher module 40 may use the hash value 92 to perform a lookup in the publisher table 72 to find the corresponding address 88. The publisher module 40 writes the address 88 into the network event data structure 86.

At operation 146, the publisher module 40 publishes the network event data structure 86 to the bus 41 based on the address 88 thereby communicating the network event data structure 86 to the appropriate processing server 38 and listener module 42. For example, all the listener modules 42 that execute on the respective processing servers 38 may receive the network event data structure 86; however, only a single listener module 42 may store the network event data structure 86 in the buffer 106. Specifically, the listener module 42 that is designated to process the address 88 associated with the network event data structure 86 may store the network event data structure 86 in the buffer 106.

At operation 148, the listener module 42 receives the network event data structure 86, analyzes the network event data structure 86 in real time, and writes the network event data structure 86 to the appropriate buffer 106. For example, the listener module 42 may analyze the network event by reading the user interface identifier 78 from the network event data structure 86 and registering the request for the user interface. The listener module 42 may register requests for a predetermined period of time to generate a report that maintains a frequency of data requests for types of user interfaces (e.g., webpage). Such a report may be used to identify the most frequently requested type of user interface, the median requested type of user interface and the least frequently requested type of interface for the period of time. In the present example, the listener module 42 may register a request for user interface that contains search results, more specifically for a user interfaces that contains search results that are generated in response to a keyword search. It will be appreciated that the analysis of the network event data structure 86 is optional. It will further be appreciated that multiple types of navigation information may be read from the network event data structure 86 and stored to generate multiple types of reports.

The listener module 42 may write the network event data structure 86 to the appropriate buffer by utilizing the network entity identifier 23 in the network event data structure 86 to identify the appropriate session bin 107 in the buffer 106. Further, the listener module 42 may copy the time 25 from the network event data structure 86 to the time 25 in the session bin 107 to register the approximate time that the network event data structure 86 was written to the buffer 106. If the listener module 42 determines that a session bin 107 does not exist for the network entity identified by the network entity identifier 23 in the network event data structure 86 then the listener module 42 may create a session bin 107.

FIG. 12 is a flow chart illustrating a method 150 to generate a network event, according to one embodiment.

At operation 151, the application 30 may store the data request 76 in the network event data structure 86 and at operation 152 the application 30 may update the time to the current time.

At decision operation 153, the application 30 determines if the client Internet protocol (IP) address 84 maps to a robot by comparing the client Internet protocol address 84 in the data request 76 to the client Internet protocol addresses 84 in the robot table 70. If a match is found, then a branch is made to operation 154. Otherwise a branch is made to operation 156.

At operation 154, the application 30 asserts the robot flag 90 in the network event data structure 86 and stores the network entity identifier 23 that is associated with the client Internet protocol (IP) address 84 in the robot table 70 in the network event data structure 86.

At operation 156, the application 30 may store flag information 94 and tag information 96 in the network event data structure 86 based on data collected from the data request 76 and at operation 157, the application 30 may store flag information 94 and tag information 96 in the network event data structure 86 based on data collected from the data response 100. For example, the flag information 94 may indicate whether the data request 76 specified to search for “exact phrases” and/or whether the data response 100 (e.g., results) included pictures. As another example, the tag information 96 may indicate whether the data request 76 specified to search in the category “toys” and/or the number of matching data items returned in the data response 100.

FIG. 13 is a flow chart illustrating a method 160 to flush a buffer 43 to a database 36, according to one embodiment. The method 160 commences at operation 162 with the listener module 42 alternating buffers 106. For example, the listener module 42 may alternate the functions of buffers 106 A and B by using one buffer 106 to store network events 86 as they arrive and the other buffer 106 to flush the network events 86 to the navigation data table 74 on the database 36.

At operation 164, the listener module 42 gets the next session bin 107 from the buffer 106. At decision operation 166, the listener module 42 determines if there are any network events 86 in the session bin 107. If there are network events 86 in the session bin 107, then a branch is made to operation 168, otherwise, processing continues at decision operation 170.

At operation 168, the listener module 42 writes the contents of the session bin 107 to the appropriate session 116 in the navigation data table 74. At decision operation 170, the listener module 42 determines whether the last network event data structure 86 was written into the session bin 107 more than thirty minutes ago. For example, the listener module 42 may determine if the current time is more than the session time threshold (e.g., thirty minutes) added to the time 25 stored in the session bin 107. Other embodiments may use a session time thresholds of shorter or longer duration. If the last network event data structure 86 was written into the session bin 107 more than thirty minutes prior, then processing continues at operation 172, otherwise processing continues at decision operation 174.

At operation 172, the listener module 42 deletes the session bin 107 in the both buffers 106 (e.g., buffer A and buffer B).

At decision operation 174, the listener module 42 determines if there are more session bins 107 to process. If there are more session bins 107 to process, processing continues at operation 162, otherwise processing ends.

FIG. 14 is a flow chart illustrating a method 180 to generate cookies, according to one embodiment. The method 182 commences at decision operation 182, at the application server 28, with the application 30 determining whether a network entity identifier 23 is included in the data request 76. Ifa network entity identifier 23 is included in the data request 76, then a branch is made to operation 184. Otherwise a branch is made to decision operation 186.

At operation 184, the application 30 generates a network entity identifier 23 and at operation 188, the application 30 adds the network entity identifier 23 to a network event data structure 86. At operation 190, the application 30 further adds the network entity identifier 23 to the data response 100.

At decision operation 186, the application 30 determines if a click count 27 is included in the data request 76. If the click count 27 is included in the data request 76, then a branch is made to operation 192. Otherwise, a branch is made to operation 194.

At operation 194, the application 30 sets the click count to one. At operation 196, the application 30 adds the click count 27 and the current time 25 to the network event data structure 86. At operation 198, the application 30 writes the click count 27 and the time 25 to the data response 100.

At operation 192, the application 30 communicates the data response 100 to the client machine 20. At operation 193, the client machine 20 may store the network entity identifier 23, the click count 27 and the time 25 as cookies on the client machine 20.

FIG. 15 is a flow chart illustrating a method 200 to identify a robot, according to one embodiment. The method 200 commences at operation 202 with the listener module 42 processing the next session bin 107.

At decision operation 204, the listener module 42 determines if there is one network event data structure 86 in the session bin 107. If there is one network event data structure 86 in the session bin 107, then a branch is made to operation 206. Otherwise, a branch is made to decision operation 208.

At operation 206, the listener module 42 saves the data request 76 in a robot work area 71 based on the client Internet protocol (IP) address 84 in the data request. At decision operation 208, the listener module 42 determines if there are more session bins 107. If there are more session bins 107, a branch is made to operation 202. Otherwise, the process ends.

FIG. 16 is a flow chart illustrating a method 220 to identify a robot. At operation 222, the listener module 42 gets the next entry in the robot work area 71.

At decision operation 224, the listener module 42 determines if the number of data requests 76 are greater than a predetermined threshold. If the number of data requests are greater than the predetermined threshold then processing continues at decision operation 226, otherwise processing continues at decision operation 228.

At decision operation 226, the listener module 42 determines if the network entity identifiers 23 are different in each data request 76. If the network entity identifiers 23 are different, then a branch is made to operation 230, otherwise, a branch is made to decision operation 228.

At operation 230, the listener module 42 has identified the client Internet protocol address 84 as being associated with a robot. Accordingly, the listener module 42 allocates a network entity identifier 23 and creates an entry in the robot table 70 that includes the network entity identifier 23 and the client Internet protocol address 84.

At decision operation 228, the listener module 42 determines if there are more entries in the robot work area 71. If there are more entries then a branch is made to operation 222, otherwise, the method 220 ends.

FIG. 17 is a block diagram of a computer system, according to one embodiment. The example computer system 400 or machine or platform includes a processor 402 (e.g., a central processing unit (CPU) a graphics processing unit (GPU) or both), a main memory 404 and a static memory 406, which communicate with each other via a bus 408. The computer system 400 may further include a video display unit 410 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)). The computer system 400 also includes an alphanumeric input device 412 (e.g., a keyboard), a cursor control device 414 (e.g., a mouse), a disk drive unit 416, a signal generation device 418 (e.g., a speaker) and a network interface device 420.

The disk drive unit 416 includes a machine-readable medium 422 on which is stored one or more sets of instructions (e.g., software 424) embodying any one or more of the methodologies or functions described herein. The software 424 may also reside, completely or at least partially, within the main memory 404 and/or within the processor 402 during execution thereof by the computer system 400, the main memory 404 and the processor 402 also constituting machine-readable media.

The software 424 may further be transmitted or received over a network 426 via the network interface device 420.

While the machine-readable medium 422 is shown in an example embodiment to be a single medium, the term “machine-readable medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “machine-readable medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present disclosure. The term “machine-readable medium” shall accordingly be taken to include, but not be limited to, solid-state memories, optical and magnetic media, and carrier wave signals.

Thus, a method and system to process navigation information have been described. Although the present disclosure has been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. 

1. A system comprising: a memory; and at least one hardware processors, the at least one hardware processor configured to perform operations comprising: receiving a data request, the data request comprising a query and a network entity identifier, the network entity identifier uniquely identifying a client device; generating a data response and network event information in response to the data request, the network event information describing the data request and the data response; associating the network entity identifier with a client internet protocol address of the client device; and identifying a network event as associated with a robot based on the client internet protocol address being associated with a different network entity identifier.
 2. The system of claim 1, wherein the operations further comprise: storing the network entity identifier associated with the client internet protocol address of the client device in a database; and updating the network event with the network entity identifier provided in a robot identification table in the database.
 3. The system of claim 1, wherein the operations further comprise: collecting a requested webpage identifier from each network event; and determining a frequency of data requests for the requested webpage identifier based on the collected requested webpage identifiers.
 4. The system of claim 1, wherein the operations further comprise: receiving a first network event associated with a first server, the first network event indicating a client identifier of the client device and a first network entity identifier, the first network entity identifier included in a first network response generated in response to a first request identifying the client device and including a first user interface identifier and not including the first network entity identifier, the first server selected to process the first request based on the first user interface identifier included in the first request; receiving a second network event associated with a second server, the second network event indicating the same client identifier of the client device and a second network entity identifier, the second network entity identifier included in a second network response generated in response to a second request identifying the client device and including a second user interface identifier and not including the second network entity identifier, the second application processing server selected to process the second request based on the second user interface identifier included in the second request; and associating the first network event and the second network event based on the same client identifier.
 5. The system of claim 4, wherein the operations further comprise: marking the client device as a robot in a database based on the association between the first network event and the second network event and the first and second network entity identifiers included with the first and second network events, respectively; determining whether the network events associated with a session indicate different client identifiers; and determining the client device is a robot in response to the network events indicating different client identifiers.
 6. The system of claim 5, wherein the first network event includes navigation information that describes a request for a keyword search of the database.
 7. The system of claim 5, wherein the operations further comprise: determining a session associated with the first network event; and grouping data derived from the first network event with other data associated with the session.
 8. The system of claim 5, wherein the operations further comprise: storing an association in the database between an Internet Protocol address of the client device and a client identifier; and generating the first network event to indicate whether the client device is indicated in the database.
 9. The system of claim 5, wherein the operations further comprise: grouping session activity of the client device to determine whether the client device is returning cookie information previously provided to the client device during the session, the session activity previously processed by multiple different application servers; and determining whether the client device is a robot based at least in part on whether the cookie information is returned.
 10. The system of claim 5, wherein the operations further comprise: analyzing network events to determine whether the data request is received from a programmatic client.
 11. A computer-implemented method to process navigation information, the method comprising: receiving a data request, the data request comprising a query and a network entity identifier, the network entity identifier uniquely identifying a client device; generating a data response and network event information in response to the data request, the network event information describing the data request and the data response; associating the network entity identifier with a client internet protocol address of the client device; and identifying a network event as associated with a robot based on the client internet protocol address being associated with a different network entity identifier.
 12. The method of claim 11, further comprising: storing the network entity identifier associated with the client internet protocol address of the client device in a database; and updating the network event with the network entity identifier provided in a robot identification table in the database.
 13. The method of claim 11, further comprising: collecting a requested webpage identifier from each network event; and determining a frequency of data requests for the requested webpage identifier based on the collected requested webpage identifiers.
 14. The method of claim 11, further comprising: receiving a first network event associated with a first server, the first network event indicating a client identifier of the client device and a first network entity identifier, the first network entity identifier included in a first network response generated in response to a first request identifying the client device and including a first user interface identifier and not including the first network entity identifier, the first server selected to process the first request based on the first user interface identifier included in the first request; receiving a second network event associated with a second server, the second network event indicating the same client identifier of the client device and a second network entity identifier, the second network entity identifier included in a second network response generated in response to a second request identifying the client device and including a second user interface identifier and not including the second network entity identifier, the second application processing server selected to process the second request based on the second user interface identifier included in the second request; and associating the first network event and the second network event based on the same client identifier.
 15. The method of claim 14, further comprising: marking the client device as a robot in a database based on the association between the first network event and the second network event and the first and second network entity identifiers included with the first and second network events, respectively; determining whether the network events associated with a session indicate different client identifiers; and determining the client device is a robot in response to the network events indicating different client identifiers.
 16. The method of claim 15, wherein the first network event includes navigation information that describes a request for a keyword search of the database.
 17. The method of claim 15, further comprising: determining a session associated with the first network event; and grouping data derived from the first network event with other data associated with the session.
 18. The method of claim 15, further comprising: storing an association in the database between an Internet Protocol address of the client device and a client identifier; and generating the first network event to indicate whether the client device is indicated in the database.
 19. The method of claim 15, further comprising: grouping session activity of the client device to determine whether the client device is returning cookie information previously provided to the client device during the session, the session activity previously processed by multiple different application servers; and determining whether the client device is a robot based at least in part on whether the cookie information is returned.
 20. A non-transitory machine-readable medium storing processor-executable instructions which, when executed by hardware processing circuitry, cause the hardware processing circuitry to perform operations comprising: receiving a data request, the data request comprising a query and a network entity identifier, the network entity identifier uniquely identifying a client device; generating a data response and network event information in response to the data request, the network event information describing the data request and the data response; associating the network entity identifier with a client internet protocol address of the client device; and identifying a network event as associated with a robot based on the client internet protocol address being associated with a different network entity identifier. 